home *** CD-ROM | disk | FTP | other *** search
- > In fact, a number of WINSOCK.DLLs do this. My application opens a number
- > of sockets (3), and in testing the stacks to see how much data we could
- > send at a time, I would get FD_WRITE messages, but in fact the send
- > would fail with SOCKET_ERROR/EWOULDBLOCK consistently. The net effect
- > was that my application would get caught in a loop, effectively hanging
- > Windows.
-
- One way to avoid the deadlock is to call PeekMessage/Dispatch/Translate
- (similar to blocking hook in SetBlockingHook() example) just before or
- after trying to receive in your FD_WRITE handler.
-
- > If anyone knows of a WINSOCK that doesn't do this, I'd like to hear about
- > it. Of course, this would probably be solved by a full 32 bit
- > implementation...
-
- Our DLL is guilty of this also. We have recently fixed it, and the
- fixed version will be available as soon as it makes it through QA.
-
- Regards,
- --
- Bob Quinn rcq@ftp.com
- FTP Software, Inc. No. Andover, MA
-
-